ts read and write (double cross over breakpoints included)#22
ts read and write (double cross over breakpoints included)#22LynxJinyangii wants to merge 5 commits into
Conversation
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
|
@LynxJinyangii I had a quick look, but there are a lot of changes so it will take me time. Very quickly. In R function documentation goes above the function when using Roxygen; no inside docstrings like in Python;) Please ensure all functions have at least some rudimentary docs so we know what the args are supposed to be (type, description, etc.). You will see in AlphaSimR that user facing functions have substantial docs, but also internal functions have some basic docs, so let's strive for that. You don't need to mark code changes by "Jinyang edited/added/changed" - we have diff tool to track this. It would be helpful if you communicate why we need another It would also be easier to review if you clearly set the intent behind the changes when you open a PR. Here is a good example gaynorr#276. Alternatively, a PR can just refer to an issue where the idea/implementation plan is laid out gaynorr#280. Can you please briefly describe your changes here so we can understand the high-level approach before we get lost in the weeds of the code review? |
|
@gregorgorjanc Thanks for the feedback. I'm currently adding ts things to runMacsTs, things at the R level (e.g. makeFoundersFromTs.R) might still change. I'll come back to documentation and comments once the core structure is more defined. Why use RecHistGen?
Main changes:
|
ts read, sampling SNPs, and write out after simulation (mainly in R)
double cross over breakpoints included (mainly in Cpp)